Seamless guest access to spaces and meetings

ABSTRACT

Seamless guest access to spaces and meetings may be provided. A trusted user device may send an identity object and may receive an identifier and an authorization token in response to sending the identity object. Then the trusted user device may send a request to add a guest user associated with the identifier to a collaboration event and may receive, in response to sending the request to add the guest user, location data associated with the collaboration event. The trusted user device may then send collaboration space data to a guest user device associated with the guest user. The collaboration space data may comprise the authorization token, the location data, and an application indicator associated with the collaboration event.

TECHNICAL FIELD

The present disclosure relates generally to access to spaces andmeetings.

BACKGROUND

A collaboration tool helps people to collaborate. The purpose of acollaboration tool is to support a group of two or more individuals toaccomplish a common goal or objective. Collaboration tools may be eitherof a non-technological nature such as paper, flipcharts, post-it notes,or whiteboards. They can also include software tools and applicationssuch as collaborative software applications.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various embodiments of the presentdisclosure. In the drawings:

FIG. 1 shows an operating environment for providing seamless guestaccess to spaces and meetings;

FIG. 2 is a flow chart of a method for providing seamless guest accessto spaces and meetings;

FIG. 3A and FIG. 3B show a flow diagram for providing seamless guestaccess to spaces and meetings;

FIG. 4A and FIG. 4B show a flow diagram for providing seamless guestaccess to spaces and meetings;

FIG. 5 is a flow chart of a method for providing seamless guest accessto spaces and meetings; and

FIG. 6 shows a computing device.

DETAILED DESCRIPTION

Overview

Seamless guest access to spaces and meetings may be provided. A trusteduser device may send an identity object and may receive an identifierand an authorization token in response to sending the identity object.Then the trusted user device may send a request to add a guest userassociated with the identifier to a collaboration event and may receive,in response to sending the request to add the guest user, location dataassociated with the collaboration event. The trusted user device maythen send collaboration space data to a guest user device associatedwith the guest user. The collaboration space data may comprise theauthorization token, the location data, and an application indicatorassociated with the collaboration event.

Both the foregoing overview and the following example embodiments areexamples and explanatory only, and should not be considered to restrictthe disclosure's scope, as described and claimed. Further, featuresand/or variations may be provided in addition to those set forth herein.For example, embodiments of the disclosure may be directed to variousfeature combinations and sub-combinations described in the exampleembodiments.

Example Embodiments

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of the disclosure may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe disclosure. Instead, the proper scope of the disclosure is definedby the appended claims.

On-demand collaboration, online meetings, web conferencing, andvideoconferencing may be provided by network conferencing applications.In addition, network conferencing applications may interconnect varioususers over a computer network for video, audio, and/or datacommunications. A host organizing a meeting may define two levels ofattendees: required and optional. When a meeting is created, authorizedattendees may receive an invitation in an email or other message. Theinvitation may have a Uniform Resource Locator (URL) or clickable linkfor joining the meeting. However, some users may later misplace orotherwise be unable to access the invitation at the time of the meeting.Other users may decide not to attend the meeting, thus may delete theinvitation. Regardless of the reason, a user may decide to participatein a meeting, but may have limited or no access to the invitation.Notwithstanding, inviting guest users to team spaces and meetings may bea difficult and time consuming process relying on emailing invitations,clicking email links, online registration, and password setting. Makingthe invitation experience more effortless for the user may create asituation in which users may be more likely to create, accept, andutilize invitations.

FIG. 1 shows an operating environment 100 consistent with embodiments ofthe disclosure for providing seamless guest access to spaces andmeetings. As shown in FIG. 1, operating environment 100 may comprise atrusted user device 102, a guest user device 104, a network 106, anidentity service 108, an application store 110, and a meeting service112. Trusted user device 102 and guest user device 104 may comprise, butare not limited to, a mobile device, a smart phone, a personal computer,a tablet device, a cable modem, a cellular base station, a telephone, aremote control device, a set-top box, a digital video recorder, aninternet of things (IoT) device, a network computer, a mainframe, arouter, or other similar microcomputer-based device.

Meeting service 112 may comprise a device or devices that may provide orhost a collaboration event consistent with embodiments of the discourse.Identity service 108 may comprise a device or devices that may providevalidation of the identity of users such as a guest user to acollaboration event consistent with embodiments of the disclosure.Application store 110 may comprise a device or devices where the guestuser may go to in order to download an application, for example, for thecollaboration event on guest user device 104. Network 106 may compriseany network (e.g., the Internet) over which trusted user device 102,guest user device 104, identity service 108, application store 110, andmeeting service 112 may communicate. Trusted user device 102 and guestuser device 104 may wirelessly communicate directly with one anotherusing, for example, Near-field Communication (NFC) protocol. Trusteduser device 102 and guest user device 104 may wirelessly communicateusing other protocols and processes and are not limited to the NFCprotocol.

The elements described above of operating environment 100 (e.g., trusteduser device 102, guest user device 104, identity service 108,application store 110, and meeting service 112) may be practiced inhardware and/or in software (including firmware, resident software,micro-code, etc.) or in any other circuits or systems. The elements ofoperating environment 100 may be practiced in electrical circuitscomprising discrete electronic elements, packaged or integratedelectronic chips containing logic gates, a circuit utilizing amicroprocessor, or on a single chip containing electronic elements ormicroprocessors. Furthermore, the elements of operating environment 100may also be practiced using other technologies capable of performinglogical operations such as, for example, AND, OR, and NOT, including butnot limited to, mechanical, optical, fluidic, and quantum technologies.As described in greater detail below with respect to FIG. 6, theelements of operating environment 100 may be practiced in a computingdevice 600.

FIG. 2 is a flow chart setting forth the general stages involved in amethod 200 consistent with embodiments of the disclosure for providingseamless guest access to spaces and meetings. Method 200 may beimplemented using trusted user device 102 as described in more detailabove with respect to FIG. 1. Ways to implement the stages of method 200will be described in greater detail below. Method 200 will be describedin conjunction with the flow diagrams of FIG. 3A, FIG. 3B, FIG. 4A, andFIG. 4B. The flow diagram of FIG. 3A and FIG. 3B illustrates embodimentsof the disclosure in which a trusted user provides identity informationassociated with a guest user. The flow diagram of FIG. 4A and FIG. 4Billustrates embodiments of the disclosure in which the trusted user doesnot provide identity information associated with the guest user.

Method 200 may begin at starting block 205 and proceed to stage 210where trusted user device 102 may send an identity object. For example,Alice may be a trusted and authorized user of identity service 108 andmeeting service 112 who wants to invite a guest user (e.g., Bob) to acollaboration event. Bob may not yet be a trusted and authorized user ofidentity service 108 and meeting service 112. The collaboration eventmay comprise, but is not limited to, a collaboration space or acollaboration meeting. Alice may have an application running on trusteduser device 102 and may use the application to send the identity objectto identity service 108. In some embodiments of the disclosure, thetrusted user (e.g., Alice) may enter the guest user's (e.g., Bob's)identity information into the application (stage 302 of FIG. 3A). Theidentity information may comprise, but is not limited to, the guestuser's email address and display name. The identity object, includingthe guest user's identity information may then be sent to identityservice 108 (stage 304 of FIG. 3A). In other embodiments, the trusteduser may not enter the guest user's identity information. In these otherembodiments, the identity object, not including the guest user'sidentity information, may be sent to identity service 108 (stage 402 ofFIG. 4A).

From stage 210, where trusted user device 102 sends the identity object,method 200 may advance to stage 220 where trusted user device 102 mayreceive, in response to sending the identity object, an identifier andan authorization token. For example, upon receiving the identity objectfrom trusted user device 102, identity service 108 may create anidentifier and an authorization token for the guest user. Withembodiments of the disclosure where the identity object included theguest user's identity information, identity service 108 may create anidentity for the guest user that has the identifier and the guest user'sidentity information (stage 306 of FIG. 3A). With embodiments of thedisclosure where the identity object did not include the guest user'sidentity information, identity service 108 may create an identity forthe guest user that has the identifier, but has place holders (i.e., ToBe Determined (TBD)) for the guest user's identity information (stage404 of FIG. 4A). Identity service 108 may then send the identifier andthe authorization token to trusted user device 102 (stage 308 of FIG. 3Aand stage 406 of FIG. 4A).

Once trusted user device 102 receives the identifier and theauthorization token in stage 220, method 200 may continue to stage 230where trusted user device 102 may send a request to add the guest userassociated with the identifier to a collaboration event. For example,the trusted user may cause trusted user device 102 to send the receivedidentifier to meeting services 112 in a request to add the guest user tothe collaboration event (e.g., meeting, space, etc.) (stage 310 of FIG.3A and stage 408 of FIG. 4A).

After trusted user device 102 sends the request to add the guest user instage 230, method 200 may proceed to stage 240 where trusted user device102 may receive, in response to sending the request to add the guestuser, location data associated with the collaboration event. Forexample, upon receiving the request to add the guest user from trusteduser device 102, meeting services 112 may send location data associatedwith the collaboration event to trusted user device 102 (stage 312 ofFIG. 3A and stage 410 of FIG. 4A). The location data may comprise, butis not limited to, an address or a Uniform Resource Locator (URL) forthe collaboration event (e.g., meeting, space, etc.). Notwithstanding,the location data may comprise any data that may be used by guest userdevice 104 to get to the collaboration event.

From stage 240, where trusted user device 102 receives the locationdata, method 200 may advance to stage 250 where trusted user device 102may send collaboration space data to guest user device 104 associatedwith the guest user. The collaboration space data may comprise theauthorization token, the location data, and an application indicatorassociated with the collaboration event. For example, the trusted user(e.g., Alice) may place trusted user device 102 near guest user device104 (i.e., “tap” guest user device 104) causing the collaboration spacedata to be transmitted to guest user device 104 over a Near-fieldCommunication (NFC) protocol (stage 314 of FIG. 3A and stage 412 of FIG.4A). Other processes may be used to send the collaboration space data toguest user device 104 and embodiments of the disclosure are not limitedto NFC. The application indicator associated with the collaborationevent may comprise, but is not limited to, a link to application store110 where the guest user may go to on guest user device 104 in order todownload an application for the collaboration event on guest user device104. Once trusted user device 102 sends the collaboration space data toguest user device 104 in stage 250, method 200 may then end at stage260.

FIG. 5 is a flow chart setting forth the general stages involved in amethod 500 consistent with embodiments of the disclosure for providingseamless guest access to spaces and meetings. Method 500 may beimplemented using guest user device 104 as described in more detailabove with respect to FIG. 1. Ways to implement the stages of method 500will be described in greater detail below. Method 500 will be describedin conjunction with the flow diagrams of FIG. 3A, FIG. 3B, FIG. 4A, andFIG. 4B. The flow diagram of FIG. 3A and FIG. 3B illustrates embodimentsof the disclosure in which a trusted user provides identity informationassociated with a guest user. The flow diagram of FIG. 4A and FIG. 4Billustrates embodiments of the disclosure in which the trusted user doesnot provide identity information associated with the guest user.

Method 500 may begin at starting block 505 and proceed to stage 510where guest user device 104 may receive the collaboration space datacomprising the authorization token, the location data, and theapplication indicator associated with the collaboration event. Forexample, trusted user device 102 may send the collaboration space datato guest user device 104 associated with the guest user over NFC.

From stage 510, where guest user device 104 receives the collaborationspace data, method 500 may advance to stage 520 where guest user device104 may download a collaboration application identified by theapplication indicator. For example, the application indicator associatedwith the collaboration event may comprise, but is not limited to, a linkto application store 110 where the guest user may go to on guest userdevice 104 in order to download an application for the collaborationevent on guest user device 104. Using this link, the guest user may goto the application store and download the application on guest userdevice 104 (stage 316 of FIG. 3A and stage 414 of FIG. 4A).

Once guest user device 104 downloads the collaboration applicationidentified by the application indicator in stage 520, method 500 maycontinue to stage 530 where guest user device 104 may send a request foran access token. The request may include the authorization token. Forexample, using guest user device 104, the guest user may persist theauthorization token received in the collaboration space data (stage 318of FIG. 3B and stage 416 of FIG. 4A). Then the guest user may send thepersisted authorization token to identity service 108 as a request forthe access token for joining the collaboration event (stage 320 of FIG.3B and stage 418 of FIG. 4A).

With embodiments of the disclosure in which the trusted user does notprovide identity information associated with the guest user, the guestuser may provide the identity information at this point in the process.For example, the trusted user (e.g., Alice) may have the identity objectcreated for the guest user (e.g., Bob) without providing personalidentity information for the guest user as described above with respectto stages 210 and 220. Identity service 108 may issue a token bound tothis identity, and the bearer of this token (e.g., the guest user) mayspecify their own identity information (e.g., email address) when thebearer first use the token. This process may allow a seamless UserInterface (UX) for the trusted user in the example case where thetrusted user may want to add many guest users in one physical conferenceroom. In this example, the trusted user may walk around the conferenceroom tapping the guest users' user devices without having to enter anyinformation about the guest users. The guest users may then confirmtheir identity information before they can join the collaboration event.

In the case where the trusted user does not provide identity informationfor the guest user, identity service 108 may see that no identityinformation has been registered for the account associated with theidentity token and may require identity information to be providedbefore the access token can be issued. Accordingly, identity service 108may send guest user device 104 a request to provide the identityinformation (stage 420 of FIG. 4B). With some embodiments of thedisclosure, the application on guest user device 104 may gather theidentity information from guest user device 104's operating system (OS)and prompt the guest user to confirm or edit for example (stage 422 ofFIG. 4B). In response to the confirmation, guest user device 104 maysend the identity information to identity service 108 (stage 424 of FIG.4B). The identity information may comprise, but is not limited to, theguest user's email address and display name. Identity service 108 mayupdate the identity for the guest user with the identity information andmay now be able to issue the access token for this identity.

After guest user device 104 sends the request for the access token instage 530, method 500 may proceed to stage 540 where guest user device104 may receive the access token. For example, in response to receivingthe request for the access token from guest user device 104 (and afterobtaining any needed identity information), identity service 108 maysend guest user device 104 the access token (stage 322 of FIG. 3B andstage 426 of FIG. 4B).

From stage 540, where guest user device 104 receives the access token,method 500 may advance to stage 550 where guest user device 104 maysend, via the application, a join request to the location indicated bythe location data. The join request may indicate a desire to join thecollaboration event and may include the access token. For example, guestuser device 104 may send the join request including the access token tothe URL associated with the location data (stage 324 of FIG. 3B andstage 428 of FIG. 4B).

After guest user device 104 sends the join request in stage 550, method500 may proceed to stage 560 where guest user device 104 may join thecollaboration event when the access token is validated. For example,meeting service 112 may validate the access token (stage 326 of FIG. 3Band stage 430 of FIG. 4B). When the access token has been validated,meeting service 112 may allow guest user device 104 to join thecollaboration event (stage 328 of FIG. 3B and stage 432 of FIG. 4B).Once guest user device 104 joins the collaboration event in stage 560,method 500 may then end at stage 570.

FIG. 6 shows a computing device 600. As shown in FIG. 6, computingdevice 600 may include a processing unit 610 and a memory unit 615.Memory unit 615 may include a software module 620 and a database 625.While executing on processing unit 610, software module 620 may performprocesses for providing seamless guest access to spaces and meetings,including for example, any one or more of the stages from method 200described above with respect to FIG. 2 and any one or more of the stagesfrom method 500 described above with respect to FIG. 5. Computing device600, for example, may provide an operating environment for trusted userdevice 102, guest user device 104, identity service 108, applicationstore 110, and meeting service 112. Trusted user device 102, guest userdevice 104, identity service 108, application store 110, and meetingservice 112 may operate in other environments and are not limited tocomputing device 600.

Computing device 600 may be implemented using a Wireless Fidelity(Wi-Fi) access point, a cellular base station, a tablet device, a mobiledevice, a smart phone, a telephone, a remote control device, a set-topbox, a digital video recorder, a cable modem, a personal computer, anetwork computer, a mainframe, a router, a switch, a server cluster, asmart TV-like device, a network storage device, a network relay device,or other similar microcomputer-based device. Computing device 600 maycomprise any computer operating environment, such as hand-held devices,multiprocessor systems, microprocessor-based or programmable senderelectronic devices, minicomputers, mainframe computers, and the like.Computing device 600 may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices. Theaforementioned systems and devices are examples and computing device 600may comprise other systems or devices.

Embodiments of the disclosure, for example, may be implemented as acomputer process (method), a computing system, or as an article ofmanufacture, such as a computer program product or computer readablemedia. The computer program product may be a computer storage mediareadable by a computer system and encoding a computer program ofinstructions for executing a computer process. The computer programproduct may also be a propagated signal on a carrier readable by acomputing system and encoding a computer program of instructions forexecuting a computer process. Accordingly, the present disclosure may beembodied in hardware and/or in software (including firmware, residentsoftware, micro-code, etc.). In other words, embodiments of the presentdisclosure may take the form of a computer program product on acomputer-usable or computer-readable storage medium havingcomputer-usable or computer-readable program code embodied in the mediumfor use by or in connection with an instruction execution system. Acomputer-usable or computer-readable medium may be any medium that cancontain, store, communicate, propagate, or transport the program for useby or in connection with the instruction execution system, apparatus, ordevice.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific computer-readable medium examples (anon-exhaustive list), the computer-readable medium may include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a portable compact disc read-only memory(CD-ROM). Note that the computer-usable or computer-readable mediumcould even be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

While certain embodiments of the disclosure have been described, otherembodiments may exist. Furthermore, although embodiments of the presentdisclosure have been described as being associated with data stored inmemory and other storage mediums, data can also be stored on or readfrom other types of computer-readable media, such as secondary storagedevices, like hard disks, floppy disks, or a CD-ROM, a carrier wave fromthe Internet, or other forms of RAM or ROM. Further, the disclosedmethods' stages may be modified in any manner, including by reorderingstages and/or inserting or deleting stages, without departing from thedisclosure.

Furthermore, embodiments of the disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. Embodiments of the disclosure may also be practicedusing other technologies capable of performing logical operations suchas, for example, AND, OR, and NOT, including but not limited to,mechanical, optical, fluidic, and quantum technologies. In addition,embodiments of the disclosure may be practiced within a general purposecomputer or in any other circuits or systems.

Embodiments of the disclosure may be practiced via a system-on-a-chip(SOC) where each or many of the elements illustrated in FIG. 1 may beintegrated onto a single integrated circuit. Such a SOC device mayinclude one or more processing units, graphics units, communicationsunits, system virtualization units and various application functionalityall of which may be integrated (or “burned”) onto the chip substrate asa single integrated circuit. When operating via a SOC, the functionalitydescribed herein with respect to embodiments of the disclosure, may beperformed via application-specific logic integrated with othercomponents of computing device 600 on the single integrated circuit(chip).

Embodiments of the present disclosure, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof the disclosure. The functions/acts noted in the blocks may occur outof the order as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

While the specification includes examples, the disclosure's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments of the disclosure.

What is claimed is:
 1. A method comprising: sending, by a trusted userdevice associated with a trusted user, an identity object; receiving, bythe trusted user device in response to sending the identity object, anidentifier and an authorization token; sending, by the trusted userdevice, a request to add a guest user associated with the identifier toa collaboration event; receiving, by the trusted user device in responseto sending the request to add the guest user, location data associatedwith the collaboration event; and sending, by the trusted user device,collaboration space data to a guest user device associated with theguest user, the collaboration space data comprising the authorizationtoken, the location data, and an application indicator associated withthe collaboration event.
 2. The method of claim 1, wherein sending theidentity object comprises sending the identity object including identityinformation of the guest user.
 3. The method of claim 1, wherein sendingthe identity object comprises sending the identity object not includingidentity information of the guest user.
 4. The method of claim 1,wherein sending the request to add the guest user associated with theidentifier to the collaboration event comprises sending the request toadd the guest user associated with the identifier to the collaborationevent comprising a collaboration space.
 5. The method of claim 1,wherein sending the request to add the guest user associated with theidentifier to the collaboration event comprises sending the request toadd the guest user associated with the identifier to the collaborationevent comprising a collaboration meeting.
 6. The method of claim 1,wherein receiving the location data comprises receiving the locationdata comprising a Uniform Resource Locator (URL).
 7. The method of claim1, wherein sending the collaboration space data to the guest user devicecomprises sending the collaboration space data to the guest user deviceover Near-field Communication (NFC) protocol.
 8. The method of claim 1,wherein sending the collaboration space data comprises sending thecollaboration space data wherein the application indicator comprises alink to an application store.
 9. A method comprising: receiving, by aguest user device, collaboration space data comprising an authorizationtoken, location data, and an application indicator associated with acollaboration event; downloading, by the guest user device, acollaboration application identified by the application indicator;sending, by the guest user device, a request for an access token, therequest including the authorization token; receiving, by the guest userdevice, the access token; sending, by the guest user device via theapplication, a join request to a location indicated by the locationdata, the join request indicating a desire to join the collaborationevent and including the access token; and joining the collaborationevent when the access token is validated.
 10. The method of claim 9,further comprising: receiving, by the guest user device in response tosending the request for the access token, a request for identityinformation associated with a guest user associated with the quest userdevice; and sending, by the guest user device in response to receivingthe request for the identity information, the identity informationassociated with the guest user, wherein receiving the access tokencomprises receiving the access token in response to sending the identityinformation.
 11. The method of claim 9, wherein receiving the accesstoken comprises receiving the access token in response to sending therequest for the access token.
 12. The method of claim 9, whereinreceiving the collaboration space data comprises receiving thecollaboration space data over Near-field Communication (NFC) protocol.13. The method of claim 9, wherein receiving the collaboration spacedata comprising the application indicator associated with thecollaboration event comprises receiving the collaboration space datacomprising the application indicator associated with the collaborationevent wherein the collaboration event comprises a collaboration space.14. The method of claim 9, wherein receiving the collaboration spacedata comprising the application indicator associated with thecollaboration event comprises receiving the collaboration space datacomprising the application indicator associated with the collaborationevent wherein the collaboration event comprises a collaboration meeting.15. The method of claim 9, wherein receiving the collaboration spacedata comprising the location data comprises receiving the collaborationspace data comprising the location data comprising a Uniform ResourceLocator (URL).
 16. An apparatus comprising: a memory storage; and aprocessing unit coupled to the memory storage, wherein the processingunit is operative to: send an identity object; receive, in response tosending the identity object, an identifier and an authorization token;send a request to add a guest user associated with the identifier to acollaboration event; receive, in response to sending the request to addthe guest user, location data associated with the collaboration event;and send collaboration space data to a guest user device associated withthe guest user, the collaboration space data comprising theauthorization token, the location data, and an application indicatorassociated with the collaboration event.
 17. The apparatus of claim 16,wherein the collaboration event comprises a collaboration space.
 18. Theapparatus of claim 16, wherein the collaboration event comprises acollaboration meeting.
 19. The apparatus of claim 16, wherein theprocessing unit being operative to send the collaboration space data tothe guest user device comprises the processing unit being operative tosend the collaboration space data to the guest user device overNear-field Communication (NFC) protocol.
 20. The apparatus of claim 16,wherein the application indicator comprises a link to an applicationstore.